Management method, management device, and management system

ABSTRACT

A computer stores connection information with respect to data items that are management targets. The connection information identifies connection sources and connection destinations. The computer executes a process including performing analysis based on the connection information with respect to first and second data, which are specified as output targets of information indicating connections; outputting first connection information as information indicating a connection between first and second data, when one or a plurality of data items that are connection destinations are traced from the first data set as a connection source, and the second data is reached as a connection destination; and outputting second connection information as information indicating a connection between third and fourth data, when one or a plurality of data items that are connection destinations are traced from the third data set as a connection source, and the fourth data is reached as a connection destination.

CROSS-REFERENCE TO RELATED APPLICATION

This patent application is based upon and claims the benefit of priorityof the prior Japanese Patent Application No. 2014-022729 filed on Feb.7, 2014, the entire contents of which are incorporated herein byreference.

FIELD

The embodiments discussed herein are related to a management method, amanagement device, and a management system.

BACKGROUND

In a data management system for managing data of a deliverable such as adocument created in a development process of a product, there is asystem in which a folder that is the storage destination of thedeliverable, may be defined in advance. For example, the storagedestinations of the deliverables that are assumed to be created in therespective stages of the development process, are defined in advance bya system administrator.

The person in charge of development creates a deliverable correspondingto a storage destination defined in advance as the development processproceeds, and stores the deliverable in the storage destination. Byrepeating such an operation in the respective stages of the developmentprocess, it is possible to manage the deliverables, such that it iseasily recognized that the deliverables needed for development arecreated without any omission.

Patent Document 1: Japanese Laid-Open Patent Publication No. 2002-182908

Patent Document 2: Japanese Laid-Open Patent Publication No. H8-292884

Patent Document 3: Japanese Laid-Open Patent Publication No. H3-46059

There are cases where the relationships between the storage destinationsand the deliverables are set, in accordance with the connections betweendevelopment operations and the connections between the components of theproduct. By setting relationships between the storage destinations andthe deliverables, the following advantage is obtained. That is, when aproblem arises in a certain component such as a failure, the range ofimpact and the factor of the failure are easily recognized by tracingalong the connections set for the deliverable relevant to the component.

Conventionally, there is provided a method of tracing back along theconnections one by one, starting from a certain data item of thedeliverable, or a folder of the storage destination. This method iseffective in confirming the connection with respect to a singledeliverable or a single storage destination; however, it is inefficientfor checking the connection between a certain data group or folder groupand another data group or folder group.

SUMMARY

According to an aspect of the embodiments, a non-transitorycomputer-readable recording medium stores a management program thatcauses a computer to execute a process, the computer being configured tostore connection information with respect to data items and folders thatare management targets, the connection information including informationidentifying connection sources and connection destinations, the processincluding performing an analysis process based on the stored connectioninformation with respect to a first data group or a first folder groupor a first mixture group of data and folders, and a second data group ora second folder group or a second mixture group of data and folders,which are specified as output targets of information indicatingconnections; outputting first connection information as informationindicating a connection between a first data item or a first folderincluded in the first data group or the first folder group or the firstmixture group of data and folders, and a second data item or a secondfolder included in the second data group or the second folder group orthe second mixture group of data and folders, when one or a plurality ofdata items or folders that are connection destinations are traced fromthe first data item or the first folder set as a connection source, andthe second data item or the second folder is reached as a connectiondestination, by the analysis process; and outputting second connectioninformation, which is different from the first connection information,as information indicating a connection between a third data item or athird folder included in the second data group or the second foldergroup or the second mixture group of data and folders, and a fourth dataitem or a fourth folder included in the first data group or the firstfolder group or the first mixture group of data and folders, when one ora plurality of data items or folders that are connection destinationsare traced from the third data item or the third folder set as aconnection source, and the fourth data item or the fourth folder isreached as a connection destination, by the analysis process.

The object and advantages of the invention will be realized and attainedby means of the elements and combinations particularly pointed out inthe appended claims. It is to be understood that both the foregoinggeneral description and the following detailed description are exemplaryand explanatory and are not restrictive of the invention as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a configuration example of a data management systemaccording to an embodiment of the present invention;

FIG. 2 illustrates an example of a hardware configuration of a datamanagement server according to an embodiment of the present invention;

FIG. 3 illustrates an example of a functional configuration of the datamanagement system according to an embodiment of the present invention;

FIG. 4 illustrates a management system of data according to anembodiment of the present invention;

FIG. 5 illustrates a configuration example of an object table stored ina data storage unit;

FIG. 6 illustrates an example of a connection table stored in the datastorage unit;

FIG. 7 illustrates the connection between objects according to anembodiment of the present invention;

FIG. 8 is a flowchart for describing an example of processing proceduresexecuted by a client device;

FIG. 9 illustrates a display example of an analysis condition inputscreen;

FIG. 10 is a display example of an analysis result output screen;

FIG. 11 is a flowchart for describing an example of processingprocedures executed by the data management server.

DESCRIPTION OF EMBODIMENTS

Preferred embodiments of the present invention will be explained withreference to accompanying drawings. FIG. 1 illustrates a configurationexample of a data management system according to an embodiment of thepresent invention. In a data management system 1 illustrated in FIG. 1,a data management server 10 and at least one client device 20 areconnected to each other via a network such as LAN (Local Area Network)or the Internet such that communication is possible.

The data management server 10 is a computer for managing data. Aplurality of computers may constitute the data management server 10. Forexample, the deliverable created by a development process of a productsuch as an electronic component of an automobile, is the data that isthe management target. The deliverable may be, for example, documentdata, drawing data, or image data. However, the data that is themanagement target need not be limited to a particular type of data.

The client device 20 is a computer used for operating on the datamanaged by the data management server 10. A PC (Personal Computer), atablet terminal, a smartphone, or a feature phone may be used as theclient device 20.

FIG. 2 illustrates an example of a hardware configuration of the datamanagement server 10 according to an embodiment of the presentinvention. The data management server 10 illustrated in FIG. 2 includesa drive device 100, a secondary storage device 102, a memory device 103,a CPU 104, and an interface device 105, which are connected to eachother via a bus B.

Programs for realizing processes at the data management server 10 areprovided by a recording medium 101. When the recording medium 101storing a program is set in the drive device 100, the program isinstalled in the secondary storage device 102 from the recording medium101 via the drive device 100. However, a program need not be installedfrom the recording medium 101; a program may be downloaded from anothercomputer via the network. The secondary storage device 102 stores theinstalled programs as well as files and data that are needed.

The memory device 103 reads a program from the secondary storage device102 and stores the program, when an instruction to activate the programis given. The CPU 104 executes functions relevant to the data managementserver 10 according to programs stored in the memory device 103. Theinterface device 105 is used as an interface for connecting to thenetwork.

Note that examples of the recording medium 101 are portable recordingmedia such as a CD-ROM, a DVD disk, and a USB memory. Furthermore,examples of the secondary storage device 102 are HDD (Hard Disk Drive)and a flash memory. Both the recording medium 101 and the secondarystorage device 102 correspond to a computer-readable recording medium.

Note that the data management server 10 may be a computer systemincluding a plurality of computers. Furthermore, the client device 20may also have hardware as illustrated in FIG. 2. Furthermore, the clientdevice 20 may include an input device for receiving input from a userand a display device for displaying information to the user.

FIG. 3 illustrates an example of a functional configuration of the datamanagement system 1 according to an embodiment of the present invention.In FIG. 3, the data management server 10 includes a request receptionunit 11, a data processing unit 12, and a response returning unit 13.These units are realized as one or more programs installed in the datamanagement server 10 cause the CPU 104 to execute processes. The datamanagement server 10 also includes a data storage unit 14. The datastorage unit 14 may be realized by, for example, the secondary storagedevice 102 or a storage device connected to the data management server10 via the network.

The request reception unit 11 receives a request to operate on data,from the client device 20. The data processing unit 12 executes aprocess according to the operation request received by the requestreception unit 11, with respect to data stored in the data storage unit14. The response returning unit 13 returns the execution results of theprocess executed by the data processing unit 12, to the client device20.

The client device 20 includes a display control unit 21, a requestsending unit 22, and a response receiving unit 23. The display controlunit 21 displays, on a display device, a screen for receiving aninstruction to operate on data that is the management target. Therequest sending unit 22 sends, to the data management server 10, anoperation request according to the operation instruction input via thescreen displayed by the display control unit 21. The response receivingunit 23 receives a response returned from the data management server 10,according to the operation request sent by the request sending unit 22.The information included in the response is displayed by the displaycontrol unit 21.

Next, a description is given of the management system of data that isthe management target, according to the present embodiment. FIG. 4illustrates a management system of data according to the presentembodiment.

In FIG. 4, a project is a concept corresponding to a single product thatis the development target. One or more processes belong to the project.A process is a concept corresponding to each stage of the developmentprocess of the product. One or more deliverable boxes belong to eachprocess. The deliverable box is a concept expressing a box for storingthe deliverable. Therefore, a deliverable belongs to a deliverable box.In the present embodiment, one deliverable box is prepared for eachdeliverable. That is to say, one deliverable may be stored in eachdeliverable box. However, a plurality of deliverables may be stored in asingle deliverable box.

As described above, in the present embodiment, the storage destinationof the deliverable is expressed by using a hierarchal structureconstituted by a project, processes, and deliverable boxes. Thishierarchal structure is referred to as a parent and child relationship.Note that data expressing a project, a process, a deliverable box, and adeliverable, is managed as records of a database in the data storageunit 14. For example, when a RDB (Relational Database) is used, aproject is managed as records of a table (hereinafter, “project table”)having a format for a project. A process is managed as records of atable (hereinafter, “process table”) having a format for a process. Adeliverable box is managed as a record of a table (hereinafter,“deliverable box table”) having a format for a deliverable box. Adeliverable is managed as a record of a table (hereinafter, “deliverabletable”) having a format for a deliverable.

Furthermore, in FIG. 4, an object is indicated as data belonging to alower layer of the deliverable. An object is an element of adeliverable, which is extracted from the deliverable, in response to auser's instruction. For example, when the deliverable is a requirementdefinition document, each requirement is extracted as one object. Thedata expressing an object is managed as a record of a database, similarto other data. Specifically, the object is managed as a record of atable (hereinafter, “object table”) having a format for an object.

For example, FIG. 5 illustrates a configuration example of an objecttable stored in the data storage unit 14.

In FIG. 5, the object table stores a record for each data item of anobject. Each record includes items such as a project name, an objectname, a deliverable name, and an object type. The project name is anidentification name of a project to which the object belongs. The objectname is an identification name of the object. The deliverable name is anidentification name of the deliverable to which the object belongs. Theobject type is information indicating the type of object. That is tosay, in the object, the type may be set according to its contents. Eachrecord may include items corresponding to other attributes.

Note that the data items of the project, the process, the deliverablebox, and the deliverable are also respectively managed by tables havinga configuration similar to that of FIG. 5. However, in a project table,there is no need for the items of the project name, the deliverablename, and the object type; the item of the object name is replaced by aproject name. Furthermore, in a process table, there is no need for theitems of the deliverable name and the object type; the item of theobject name is replaced by an identification name of a process(hereinafter, “process name”). Furthermore, in a deliverable box table,there is no need for the item of the object type; the item of the objectname is replaced by an identification name of a deliverable box(hereinafter, “deliverable box name”). Furthermore, the item of thedeliverable name is replaced by a process name of a process to which thedeliverable box belongs. Furthermore, in a deliverable table, there isno need for the item of the object type; the item of the object name isreplaced by a deliverable name. Furthermore, the item of the deliverablename is replaced by a deliverable box name of a deliverable box to whichthe deliverable belongs.

Alternatively, the record of each table may include, as information foridentifying data to be stored in the record, data names of all datarecursively tracing back to the parent of the corresponding data, inaddition of the data name of the corresponding data. For example, in thecase of a project table, the project name is included. In a processtable, the project name and the process name are included. In adeliverable box table, the project name, the process name, and thedeliverable box name are included. In a deliverable table, the projectname, the process name, the deliverable box name, and the deliverablename are included.

In the present embodiment, “data” is a record of a project, a process, adeliverable box, a deliverable, and an object. Among these, the project,the process, and the deliverable box are data constituting the storagedestination of the deliverable, and are thus expressed as a folder withrespect to the user. That is to say, a project is expressed as a folderstoring one or more processes. A process is expressed as a folderstoring one or more deliverable boxes. A deliverable box is expressed asa folder storing one deliverable. Thus, in the present embodiment, a“folder” is used as a term meaning the highest conception of a project,a process, and a deliverable box.

Furthermore, in the present embodiment, the concept of distinguishing aproject, a process, a deliverable box, a deliverable, and an object isreferred to as a data type.

The parent and child relationship of the project, the process, thedeliverable box, etc., is defined in advance by, for example, anadministrator. The developer of a product creates a deliverablecorresponding to the deliverable box as the development processproceeds, and registers the deliverable in the deliverable box.Accordingly, it is possible to manage the deliverables, such that it iseasily recognized that the deliverables needed for development arecreated without any omission.

Between the respective data items, a connection may be set. One of thetwo data items connected by one connection is the connection source, andthe other data item is the connection destination. That is to say, thereis a direction in a connection. The direction from the connection sourceto the connection destination is hereinafter referred to as “forwarddirection”. The direction from the connection destination to theconnection source is hereinafter referred to as “backward direction”.

The connection is also managed as a record of a table (hereinafter,“connection table”) for managing connections in the data storage unit14, similar to the data. A record of connection includes anidentification name of the data of the connection source (hereinafter,“data name”), and the data name of the data of the connectiondestination. The data name is the highest conception of the projectname, the process name, the deliverable box name, the deliverable name,and the object name. Note that in the present embodiment, as a matter ofconvenience, connection is not included in the concept of “data”.

FIG. 6 illustrates an example of a connection table stored in the datastorage unit 14. The connection table illustrated in FIG. 6 includesitems such as the connection source, the connection destination, anattribute 1, and an attribute 2, for each connection. The connectionsource is the data name of the data that is the connection source. Theconnection destination is the data name of the data of the connectiondestination. The attribute 1 and the attribute 2 are examples ofattributes of connection. By the connection table, it is possible toidentify the connection source and the connection destination, withrespect to the connection between data items.

Note that the connection source and the connection destination of eachrecord illustrated in FIG. 6 are both object names. That is to say, therecord illustrated in FIG. 6 is a record for managing the connectionbetween objects. However, the connection may be set between data itemsbelonging to data types other than an object. For example, a connectionmay be set between processes. Furthermore, the connection may be setacross different data types. For example, a connection may be setbetween a process and a deliverable.

Note that the connection indicated by the object table of FIG. 5 and theconnection table of FIG. 6 is visually indicated in FIG. 7.

FIG. 7 illustrates the connection between objects according to anembodiment of the present invention. In FIG. 7, when the type of anobject is “type 1”, the object is indicated by an oval. When the type ofan object is “type 3”, the object is indicated by a rectangle. Theconnection between objects is indicated by an arrow. The object at thesource of the arrow is the connection source, and the object at thepoint of the arrow is the connection destination.

Note that the connection between data and the parent and childrelationship constituting the hierarchal structure of FIG. 4 aredifferent concepts, and are managed in different formats in terms ofdata management. For example, the parent and child relationship betweena deliverable and an object is managed by a “deliverable name” item inthe object table. Meanwhile, the connection between data is managed bythe connection table. The connection between data may be arbitrarily setacross the parent and child relationship of data.

In the present embodiment, in response to a request from the clientdevice 20, the data management server 10 executes analysis of theconnection between a certain data group and another data group.

In the following, a description is given of processing procedures thatare executed in the data management system 1. FIG. 8 is a flowchart fordescribing an example of processing procedures executed by the clientdevice 20.

In step S101, the display control unit 21 receives a setting of analysisconditions from the user, via an analysis condition input screen.

FIG. 9 illustrates a display example of an analysis condition inputscreen. In FIG. 9, an analysis condition input screen 510 includes atype selection area 511, a button 512, a button 513, a vertical axistype display area 514, a horizontal axis type display area 515, and anOK button 516.

The type selection area 511 displays a list of data types as options.However, as for objects, options are displayed for each object type. Inthe type selection area 511, when the button 512 is pressed in a statewhere any one of the options is selected, the data type or object typerelevant to the option being selected is displayed in the vertical axistype display area 514. In the type selection area 511, when the button513 is pressed in a state where any one of the options is selected, thedata type or object type relevant to the option being selected isdisplayed in the horizontal axis type display area 515. Note that themeanings of vertical axis and horizontal axis are described below. Inthe analysis condition input screen 510, the data type or object typearranged along the vertical axis, and the data type or object typearranged along the horizontal axis, are selected as parametersconstituting the analysis conditions. Note that the same data type orobject type may be selected for both the vertical axis and thehorizontal axis.

The data type or object type selected for the vertical axis ishereinafter referred to as a “vertical axis type”. Furthermore, the datatype or object type selected for the horizontal axis is hereinafterreferred to as a “horizontal axis type”. The vertical axis type and thehorizontal axis type are information specifying a data group that is theanalysis target of connection and the display target of analysisresults. The example of FIG. 9 illustrates a case where one of theobject types “type 1” is selected as the vertical axis type, and anotherone of the object types “type 3” is selected as the horizontal axistype.

When the OK button 516 is pressed after both the vertical axis type andthe horizontal axis type are selected, the request sending unit 22 sendsan analysis request including the vertical axis type and the horizontalaxis type, to the data management server 10 (step S102). In response tothis analysis request, the data processing unit 12 of the datamanagement server 10 executes an analysis process with respect to theconnection between a group of data belonging to the vertical axis typeand a group of data belonging to the horizontal axis type. Details ofthe analysis process are described below.

Next, the response receiving unit 23 receives information indicating theanalysis results obtained by the data processing unit 12 (step S103).Next, the display control unit 21 causes the display device to displayan analysis result output screen including information indicating theanalysis results (step S104).

FIG. 10 is a display example of an analysis result output screen. InFIG. 10, an analysis result output screen 520 includes a tableindicating a matrix including four rows and three columns, in which fourdata items belonging to the vertical axis type are arranged in the linedirection (vertical axis direction), and three data items belonging tothe horizontal axis type are arranged in the row direction (horizontalaxis direction). The elements of the matrix are “↑”, “←”, “x”, or ablank space.

“↑” indicates that there is a direct or indirect connection, in whichthe data arranged in the line of the element is the connection source,and the data arranged in the row of the element is the connectiondestination. A direct connection means a state where two data items areconnected by one connection. An indirect connection means that two dataitems are connected by a plurality of connections. That is to say, “↑”indicates that by tracing along one or more connections in the forwarddirection from the data arranged in the line of the element, it ispossible to arrive at (reach) the data arranged in the row of theelement.

“←” indicates that there is a direct or indirect connection, in whichthe data arranged in the row of the element is the connection source,and the data arranged in the line of the element is the connectiondestination. That is to say, “←” indicates that by tracing along one ormore connections in the forward direction from the data arranged in therow of the element, it is possible to arrive at (reach) the dataarranged in the line of the element. Alternatively, “←” may indicatethat there is a direct or indirect connection, in which the dataarranged in the line of the element is the connection destination, andthe data arranged in the row of the element is the connection source.That is to say, “←” indicates that by tracing along one or moreconnections in the backward direction (i.e., by tracing back along theconnections) from the data arranged in the line of the element, it ispossible to arrive at (reach) the data arranged in the row of theelement.

“x” indicates that by tracing along the connections in either theforward direction or the backward direction from the data arranged inthe line of the element, it is not possible to arrive at the dataarranged in the row of the element, but by tracing along the connectionsin directions including a mixture of the forward direction and thebackward direction, it is possible to arrive at the data arranged in therow of the element.

A blank space indicates that none of “↑”, “←”, or “x” apply. That is tosay, a blank space indicates that there is no connection between thedata arranged in the line of the element and the data arranged in therow of the element.

With reference to FIG. 7, a specific description is given of theconnection between objects indicated by the elements of “↑”, “←”, and“x” in FIG. 10. The element of “↑” indicating the connection betweenObjA and Obj1 in FIG. 10, is based on the connections in the forwarddirection constituted by ObjA→ObjB→Obj1 in FIG. 7. The element of “↑”indicating the connection between ObjA and Obj2 in FIG. 10, is based onthe connections in the forward direction constituted byObjA→ObjB→Obj1→Obj2 in FIG. 7. The element of “x” indicating theconnection between ObjA and Obj3 in FIG. 10, is based on the connectionsincluding both the forward direction and the backward directionconstituted by ObjA→ObjD←Obj3 in FIG. 7.

The element of “↑” indicating the connection between ObjB and Obj1 inFIG. 10, is based on the connection constituted by ObjB→Obj1 in FIG. 7.The element of “↑” indicating the connection between ObjB and Obj2 inFIG. 10, is based on the connections constituted by ObjB→Obj1→Obj2 inFIG. 7.

The element of “←” indicating the connection between ObjD and Obj3 inFIG. 10, is based on the connection in the backward constituted byObjD←Obj3 in FIG. 7.

As described above, according to the analysis result output screen 520illustrated in FIG. 10, the user may intuitively and visually recognizethe connection between the data constituting the group of data belongingto the vertical axis type and the data constituting the group of databelonging to the horizontal axis type. As a result, for example, theuser may easily recognize a failure and the range of the impact of afailure of a component corresponding to certain data. Furthermore, theuser may easily detect that a connection, which is not supposed to beallowed, is set. For example, in a case where the setting of aconnection corresponding to “x” is not allowed, the user may revise thesetting relevant to the connection.

Next, a description is given of processing procedures executed by thedata management server 10. FIG. 11 is a flowchart for describing anexample of processing procedures executed by the data management server10.

In step S201, the request reception unit 11 receives an analysis requestsent in step S102. Next, the data processing unit 12 searches, the datastorage unit 14, for data belonging to the vertical axis type includedin the analysis request (step S202). When the vertical axis typeindicates the data type, the data processing unit 12 searches allrecords of the table corresponding to the data type. When the verticalaxis type indicates the object type, the data processing unit 12searches records whose object type matches the vertical axis type, in anobject table.

Next, the data processing unit 12 searches the data storage unit 14 fordata belonging to the horizontal axis type included in the analysisrequest (step S203). The method of searching for data belonging to thehorizontal axis type may be the same as the method of searching for databelonging to the vertical axis type.

Next, the data processing unit 12 assigns, in a variable Vn, the numberof data items found by the search in step S202, and assigns, in avariable Hn, the number of data items found by the search in step S203(step S204).

Next, the data processing unit 12 assigns 1 to a variable v and to avariable h, respectively (step S205). The variable v is for identifyingthe data that is the processing target in the group of data belonging tothe vertical axis type. The variable h is for identifying the data thatis the processing target in the group of data belonging to thehorizontal axis type. In the following, the with data item in the groupof data belonging to the vertical axis type is referred to “data v”.Furthermore, the hth data item in the group of data belonging to thehorizontal axis type is referred to “data h”.

Next, the data processing unit 12 refers to the connection table (FIG.6), and determines whether it is possible to reach the data h, bytracing along one or more connections in the forward direction, from thedata v that is the connection source (step S206). When it is possible toreach the data h (YES in step S206), the data processing unit 12 stores“V” as information indicating the connection between data v and data h.The storage destination of this information is, for example, the memorydevice 103 or the secondary storage device 102. “V” corresponds to “↑”in FIG. 10. That is to say, the display control unit 21 replaces “V”with “↑” and displays “↑”. However, “V” may be displayed without beingreplaced.

Note that whether it is possible to reach data h by referring to theconnection table and tracing along one or more connections in theforward direction, from the data v that is the connection source, may bedetermined as follows, for example.

(1) Search the connection table for a record including data v as theconnection source.

(2) Search the connection table for a record including, as theconnection source, the connection destination of the record found as aresult of the search.

(3) Recursively repeat (2) with respect to the record found as a resultof the search. When a record including data h as the connectiondestination is found before there are no more records to be searched, itmeans that data h is reached. When there are no more records to besearched without finding a corresponding record, it means that data h isnot reached.

When data h is not reached (NO in step S206), the data processing unit12 refers to the connection table, and determines whether it is possibleto reach the data v, by tracing along one or more connections theforward direction, from the data h that is the connection source (stepS208). That is to say, it is determined whether there is a connection inthe direction opposite to the connection found as a result of the searchin step S206.

When data v is reached (YES in step S208), the data processing unit 12stores “H”, which is different from “V”, as information indicating theconnection between data v and data h. “H” corresponds to “←” in FIG. 10.That is to say, the display control unit 21 replaces “H” with “←” anddisplays “←”. However, “H” may be displayed without being replaced. Notethat the determination method in step S208 may be performed by, forexample, (1) through (3) described with reference to step S206 exceptthat data v and data h are replaced with each other.

When data v is not reached (NO in step S208), the data processing unit12 refers to the connection table, and determines whether it is possibleto reach the data h, by tracing along one or more connections in eitherthe forward direction or the backward direction, from the data v that isthe connection source or the connection destination (step S210). Whendata h is reached (YES in step S210), the data processing unit 12 stores“M”, which is different from “V” or “H”, as information indicating theconnection between data v and data h. “M” corresponds to “x” in FIG. 10.That is to say, the display control unit 21 replaces “M” with “x” anddisplays “x”. However, “M” may be displayed without being replaced.

Note that whether it is possible to reach data h by referring to theconnection table illustrated in FIG. 6 and tracing along one or moreconnections in either the forward direction or the backward direction,from the data v that is the connection source or the connectiondestination, may be determined as follows, for example.

(1) Search the connection table for a record including data v as theconnection source or the connection destination.

(2) Search the connection table for a record including, as connectionsource or the connection destination, the connection source or theconnection destination of the record found as a result of the search.

(3) Recursively repeat (2) with respect to the record found as a resultof the search. When a record including data h as the connection sourceor the connection destination is found before there are no more recordsto be searched, it means that data h is reached. When there are no morerecords to be searched without finding a corresponding record, it meansthat data h is not reached.

When data h is not reached (NO in step S210), the data processing unit12 stores “0” as the analysis result with respect to data v and data h.“0” corresponds to a blank space in FIG. 10. That is to say, the displaycontrol unit 21 replaces the analysis result “0” with a blank space.However, “0” may be displayed without being replaced.

After any one of steps S207, S209, S211, S212, the data processing unit12 determines whether the value of a variable h is greater than or equalto a variable Hn (step S213). That is to say, the data processing unit12 determines, with respect to data v, whether analysis of connectionshas been performed for all data belonging to the horizontal axis type.When the value of the variable h is less than the variable Hn (NO instep S213), the data processing unit 12 increments the variable h by one(step S214), and repeats step S206 and onward. That is to say, theconnection with the data v is analyzed for the next data item belongingto the horizontal axis type.

When the value of the variable h is greater than or equal to thevariable Hn (YES in step S213), the data processing unit 12 determineswhether the value of the variable v is greater than or equal to thevariable Vn (step S215). That is to say, the data processing unit 12determines, with respect to data v, whether analysis of connections hasbeen performed for all data belonging to the vertical axis type. Whenthe value of the variable v is less than the variable Vn (NO in stepS215), the data processing unit 12 increments the variable v by one,assigns one in the variable h (step S216), and repeats step S206 andonward. That is to say, the connection with all of the data belonging tothe horizontal axis type is analyzed for the next data item belonging tothe vertical axis type.

When the value of the variable v is greater than or equal to thevariable Vn (YES in step S215), the response returning unit 13 returnsthe stored analysis results to the client device 20 (step S217). That isto say, the response returning unit 13 outputs the analysis results.However, the destination to which the analysis results are sent may be,for example, a mail address specified in the analysis request. That isto say, the analysis results may be sent by e-mail. In this case, theanalysis results are generated as, for example, the table format dataindicating a matrix as illustrated in FIG. 10, and the table format datamay be attached to the e-mail. Alternatively, the e-mail may include aURL (Uniform Resource Locator) by which the analysis may be referred to,and a web page indicating the analysis results may be returned inresponse to a request to the URL.

Note that in the above description, as a matter of convenience, specificexamples are given of the connection between objects; however, as forthe connection between data belonging to other data types, the analysismay be performed by the same processing procedures as above. Therefore,in the present embodiment, the connection may be analyzed for data thatis classified into folders of projects, processes, and deliverableboxes.

As described above, according to the present embodiment, with respect toa certain data group or folder group or a mixture group of data andfolders, and another data group or folder group or a mixture group ofdata and folders, it is possible to automatically analyze and output theconnection between data items or between folders or between each dataitem and each folder. Therefore, efficiency is increased with respect tothe checking of connections between a certain data group or a foldergroup and another data group or folder group.

Note that the scope to which the present embodiment is applicable is notlimited to the data group or folder group managed in the managementformat as illustrated in FIG. 4. For example, in a management format ofa typical file system, if it is possible to set the connection betweenfiles or folders, the present embodiment may be applied to the filegroup or folder group.

Furthermore, in the present embodiment, a description is given of anexample in which the group of data arranged along the vertical axis(line direction) and the group of data arranged along the horizontalaxis (row direction) are selected in units of the data type or objecttype. However, for example, it may be possible to select data or foldersarranged along the vertical axis and data or folders arranged along thehorizontal axis, one by one, in units of data or in units of folders.That is to say, the method of selecting a data group or a folder grouparranged along the vertical axis and a data group or a folder grouparranged along the horizontal axis, is not limited to a predeterminedmethod.

Furthermore, the analysis condition input screen 510 and the analysisresult output screen 520 may be generated by the response returning unit13 by using, for example, HTML (HyperText Markup Language). In thiscase, the client device 20 is to have a versatile web browser.

Alternatively, the functions of the data processing unit 12 may beincluded in each client device 20. That is to say, the processingprocedures illustrated in FIG. 11 may be executed by the client device20. In this case, each client device 20 may search for data from thedata management server 10 via the network.

Note that in the present embodiment, the data management server 10 is anexample of a management system. The data processing unit 12 is anexample of an analysis unit. The response returning unit 13 or thedisplay control unit 21 is an example of an output unit. The connectiontable is an example of connection information. “V” or “↑” that is anexample of connection information, is an example of first connectioninformation. “H” or “←” is an example of second connection information.“M” or “x” is an example of third connection information.

The present invention is not limited to the specific embodimentsdescribed herein, and variations and modifications may be made withoutdeparting from the scope of the present invention.

According to an aspect of the embodiments, it is possible to increasethe efficiency in checking the connection between a certain data groupor folder group and another data group or folder group.

All examples and conditional language recited herein are intended forpedagogical purposes to aid the reader in understanding the inventionand the concepts contributed by the inventor to furthering the art, andare to be construed as being without limitation to such specificallyrecited examples and conditions, nor does the organization of suchexamples in the specification relate to a showing of the superiority andinferiority of the invention. Although the embodiments of the presentinvention have been described in detail, it should be understood thatthe various changes, substitutions, and alterations could be made heretowithout departing from the spirit and scope of the invention.

What is claimed is:
 1. A non-transitory computer-readable recordingmedium storing a management program that causes a computer to execute aprocess, the computer being configured to store connection informationwith respect to objects and folders representing a hierarchicallocation, the objects and the folders being management targetsmaintained in hierarchical structure, the connection informationincluding information identifying connection sources and connectiondestinations, the process comprising: performing an analysis processbased on the stored connection information with respect to a first groupindicating a first object group or a first folder group at a firsthierarchical location or a first mixture group of objects and folders atthe first hierarchical location, and a second group indicating a secondobject group or a second folder group at a second hierarchical locationor a second mixture group of objects and folders at the secondhierarchical location, which are specified as output targets ofinformation indicating connections; determining, as a forward direction,a connection between management targets in a combination, for eachcombination of a first management target reaching to one secondmanagement target and the one second management target to which thefirst management target reaches, upon reaching the one second managementtarget that is either one of the object or the folder included in thesecond group as a connection destination by the analysis process, inwhich one or a plurality of objects or folders that are connectiondestinations are traced from each of one or more first managementtargets being the object or the folder included in the first group setas a connection source; determining, as a backward direction, aconnection between management targets in a combination, for eachcombination of a third management target reaching to one fourthmanagement target and the one fourth management target to which thethird management target reaches, upon reaching the one fourth managementtarget that is either one of the object or the folder included in thefirst group as a connection destination by the analysis process, inwhich one or a plurality of objects or folders that are connectiondestinations are traced from each of one or more third managementtargets being the object or the folder included in the second group setas a connection source; determining, as a mixture of the forwarddirection and the backward direction, a connection between a fifthmanagement target that is either one of the object or the folderincluded in the first object group or the first folder group or thefirst mixture group of object and folders, and a sixth management targetthat is either one of the object or the folder included in the secondobject group or the second folder group or the second mixture group ofobject and folders; and displaying, at a display device, a matrix of thefirst group and the second group indicated as output targets, the matrixindicating each connection by the determined forward direction, thedetermined backward direction, or the mixed direction.
 2. Thenon-transitory computer-readable recording medium according to claim 1,the process further comprising: upon reaching the sixth managementtarget as being connected to the fifth management target by the analysisprocess, in which one or a plurality of folders, which may be eitherconnection destinations or connection sources of the fifth managementtarget, are traced, but the sixth management target is unreached bytracing one or a plurality of folders that are connection destinationsof the fifth management target, and the sixth management target isunreached by tracing one or a plurality of folders that are connectionsources of the fifth management target.
 3. A management method executedby a computer configured to store connection information with respect toobjects and folders representing a hierarchical location, the objectsand the folders being management targets maintained in hierarchicalstructure, the connection information including information identifyingconnection sources and connection destinations, the management methodcomprising: performing an analysis process based on the storedconnection information with respect to a first group indicating a firstobject group or a first folder group at a first hierarchical location ora first mixture group of objects and folders at the first hierarchicallocation, and a second group indicating a second object group or asecond folder group at a second hierarchical location or a secondmixture group of objects and folders at the second hierarchicallocation, which are specified as output targets of informationindicating connections; determining, as a forward direction, aconnection between management targets in a combination, for eachcombination of a first management target reaching to one secondmanagement target and the one second management target to which thefirst management target reaches, upon reaching the one second managementtarget that is either one of the object or the folder included in thesecond group as a connection destination by the analysis process, inwhich one or a plurality of objects or folders that are connectiondestinations are traced from each of one or more first managementtargets being the object or the folder included in the first group setas a connection source; determining, as a backward direction, aconnection between management targets in a combination, for eachcombination of a third management target reaching to one fourthmanagement target and the one fourth management target to which thethird management target reaches, upon reaching the one fourth managementtarget that is either one of the object or the folder included in thefirst group as a connection destination by the analysis process, inwhich one or a plurality of objects or folders that are connectiondestinations are traced from each of one or more third managementtargets being the object or the folder included in the second group setas a connection source; determining, as a mixture of the forwarddirection and the backward direction, a connection between a fifthmanagement target that is either one of the object or the folderincluded in the first object group or the first folder group or thefirst mixture group of object and folders, and a sixth management targetthat is either one of the object or the folder included in the secondobject group or the second folder group or the second mixture group ofobject and folders; and displaying, at a display device, a matrix of thefirst group and the second group indicated as output targets, the matrixindicating each connection by the determined forward direction, thedetermined backward direction, or the mixed direction.
 4. The managementmethod according to claim 3, further comprising: upon reaching the sixthmanagement target as being connected to the fifth management target bythe analysis process, in which one or a plurality of folders, which maybe either connection destinations or connection sources of the fifthmanagement target, are traced, but the sixth management target isunreached by tracing one or a plurality of folders that are connectiondestinations of the fifth management target, and the sixth managementtarget is unreached by tracing one or a plurality of folders that areonly connection sources of the fifth management target.
 5. A managementdevice configured to store connection information with respect toobjects and folders representing a hierarchical location, the objectsand the folders being management targets maintained in hierarchicalstructure, the connection information including information identifyingconnection sources and connection destinations, the management devicecomprising: a processor configured to execute a process includingperforming an analysis process based on the stored connectioninformation with respect to a first group indicating a first objectgroup or a first folder group at a first hierarchical location or afirst mixture group of objects and folders at the first hierarchicallocation, and a second group indicating a second object group or asecond folder group at a second hierarchical location or a secondmixture group of objects and folders at the second hierarchicallocation, which are specified as output targets of informationindicating connections, determining, as a forward direction, aconnection between management targets in a combination, for eachcombination of a first management target reaching to one secondmanagement target and the one second management target to which thefirst management target reaches, upon reaching the one second managementtarget that is either one of the object or the folder included in thesecond group as a connection destination by the analysis process, inwhich one or a plurality of objects or folders that are connectiondestinations are traced from each of one or more first managementtargets being the object or the folder included in the first group setas a connection source, determining, as a backward direction, aconnection between management targets in a combination, for eachcombination of a third management target reaching to one fourthmanagement target and the one fourth management target to which thethird management target reaches, upon reaching the one fourth managementtarget that is either one of the object or the folder included in thefirst group as a connection destination by the analysis process, inwhich one or a plurality of objects or folders that are connectiondestinations are traced from each of one or more third managementtargets being the object or the folder included in the second group setas a connection source, determining, as a mixture of the forward and thebackward direction, a connection between a fifth management target thatis either one of the object or the folder included in the first objectgroup or the first folder group or the first mixture group of object andfolders, and a sixth management target that is either one of the objector the folder included in the second object group or the second foldergroup or the second mixture group of object and folders, and displaying,at a display device, a matrix of the first group and the second groupindicated as output targets, the matrix indicating each connection bythe determined forward direction, the determined backward direction, orthe mixed direction.
 6. The management device according to claim 5, theprocess further comprising: upon reaching the sixth management target asbeing connected to the fifth management target by the analysis process,in which one or a plurality of folders, which may be either connectiondestinations or connection sources of the fifth management target, aretraced, but the sixth management target is unreached by tracing one or aplurality of folders that are only connection destinations of the fifthmanagement target, and the sixth management target is unreached bytracing one or a plurality of folders that are only connection sourcesof the fifth management target.
 7. A management system configured tostore connection information with respect to objects and foldersrepresenting a hierarchical location, the objects and the folders beingmanagement targets maintained in hierarchical structure, the connectioninformation including information identifying connection sources andconnection destinations, the management system comprising: a processorconfigured to execute a process including performing an analysis processbased on the stored connection information with respect to a first groupindicating a first object group or a first folder group at a firsthierarchical location or a first mixture group of objects and folders atthe first hierarchical location, and a second group indicating a secondobject group or a second folder group at a second hierarchical locationor a second mixture group of objects and folders at the secondhierarchical location, which are specified as output targets ofinformation indicating connections, determining as a forward direction aconnection between management targets in a combination, for eachcombination of a first management target reaching to one secondmanagement target and the one second management target to which thefirst management target reaches, upon reaching the one second managementtarget that is either one of the object or the folder included in thesecond group as a connection destination by the analysis process, inwhich one or a plurality of objects or folders that are connectiondestinations are traced from each of one or more first managementtargets being the object or the folder included in the first group setas a connection source; determining, as a backward direction, aconnection between management targets in a combination, for eachcombination of a third management target reaching to one fourthmanagement target and the one fourth management target to which thethird management target reaches, upon reaching the one fourth managementtarget that is either one of the object or the folder included in thefirst group as a connection destination by the analysis process, inwhich one or a plurality of objects or folders that are connectiondestinations are traced from each of one or more third managementtargets being the object or the folder included in the second group setas a connection source; determining, as a mixture of the forward and thebackward direction, a connection between a fifth management target thatis either one of the object or the folder included in the first objectgroup or the first folder group or the first mixture group of object andfolders, and a sixth management target that is either one of the objector the folder included in the second object group or the second foldergroup or the second mixture group of object and folders; and displaying,at a display device, a matrix of the first group and the second groupindicated as output targets, the matrix indicating each connection bythe determined forward direction, the determined backward direction, orthe mixed direction.
 8. The management system according to claim 7, theprocess further comprising: upon reaching the sixth management target asbeing connected to the fifth management target by the analysis process,in which one or a plurality of folders, which may be either connectiondestinations or connection sources of the fifth management target, aretraced, but the sixth management target is unreached by tracing one or aplurality of folders that are connection destinations of the fifthmanagement target, and the sixth management target is unreached bytracing one or a plurality of folders that are only connection sourcesof the fifth management target.